Systems and method for coordinating trend data via a hub

ABSTRACT

A system includes a non-transitory memory and one or more hardware processors configured to perform operations including receiving, via a product model API, product model data for a product sold by a vendor, receiving from the vendor, via an offer API, offer data corresponding to one or more promotional offers for the product, processing, via a deal hub, the offer data, generating a catalog item for the product, and displaying the catalog item within a catalog.

BACKGROUND

This section is intended to introduce the reader to various aspects ofart that may be related to aspects of the present disclosure, which aredescribed and/or claimed below. This discussion is believed to behelpful in providing the reader with background information tofacilitate a better understanding of the various aspects of the presentdisclosure. Accordingly, it should be understood that these statementsare to be read in this light, and not as admissions of prior art.

An enterprise may utilize multiple platforms to conduct its operations.For example, the enterprise may use a first platform for human resources(HR), a second platform for payroll, a third platform for purchasing, afourth platform for information technology (IT) (e.g., email,networking, data storage, computer logins), and a fifth platform foraccounting. Due to differences in data formatting and communicationprocesses, data sharing between platforms may be difficult and/or resultin inefficiencies. For example, in order to achieve data sharing betweenone or more platforms, the enterprise may assign an in-house developer,or hire an outside developer (e.g., a contractor or a softwaredevelopment services company) to write scripts to facilitate the sharingof data between platforms. As the platforms update and evolve over time,the scripts may be correspondingly updated to account for the changes tothe platforms.

SUMMARY

A summary of certain embodiments disclosed herein is set forth below. Itshould be understood that these aspects are presented merely to providethe reader with a brief summary of these certain embodiments and thatthese aspects are not intended to limit the scope of this disclosure.Indeed, this disclosure may encompass a variety of aspects that may notbe set forth below.

The disclosed techniques include configurable adapters that may be usedin conjunction with middleware to share data between various platformsand/or applications without a user, developer, or IT agent writing oneor more scripts to facilitate the sharing of data. Further, as variousplatforms and applications are updated, the configurable adapters andmiddleware may also dynamically update so a user does not have to spendtime updating a script to work with the updated platforms/applications.Using configurable adapters and middleware, large complex frameworks ofmany platforms/applications may be designed to perform various functionsof an enterprise or organization. For example, such a framework may bedesigned to pull or receive product information from various vendors orthird parties, as well as promotional offers for those products. Theproduct and offer data may be combined, processed, and listed in aproduct catalog, which users may use to shop for and order products orservices. The configurable adapters and middleware may be used to allowplatforms and/or applications used by the enterprise to share data aboutthe order and create appropriate records (e.g., for book keeping,accounting, taxes, facilities, etc.). Accordingly, the use ofconfigurable adapters and middleware may significantly reduce or eveneliminate the amount of script writing and other software developmentdone to create a complex framework of platforms and/or applications toperform complex tasks within an enterprise.

Various refinements of the features noted above may exist in relation toaspects of the present disclosure. Further features may also beincorporated in these various aspects as well. These refinements andadditional features may exist individually or in any combination. Forinstance, various features discussed below in relation to one or more ofthe illustrated embodiments may be incorporated into any of theabove-described aspects of the present disclosure alone or in anycombination. The brief summary presented above is intended only tofamiliarize the reader with certain aspects and contexts of embodimentsof the present disclosure without limitation to the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

The description herein makes reference to the accompanying drawings,wherein like reference numerals refer to like parts throughout theseveral views.

FIG. 1 is a block diagram of a distributed computing system utilizing acloud service and a database, in accordance with an embodiment;

FIG. 2 is a block diagram of a generalized computing device utilized inthe distributed computing system of FIG. 1, in accordance with anembodiment;

FIG. 3 is a block diagram of an embodiment of a system for exchangingdata between two or more platforms, in accordance with an embodiment;

FIG. 4 is a screen shot from a configurable adapter set up screen, inaccordance with an embodiment;

FIG. 5 is a screen shot of the configurable adapter set up screen ofFIG. 4 when a priority field is selected, in accordance with anembodiment;

FIG. 6 is a screen shot of the configurable adapter set up screen ofFIG. 4 when an impact field is selected, in accordance with anembodiment;

FIG. 7 is a screen shot of the configurable adapter set up screen ofFIG. 4 when a state field is selected, in accordance with an embodiment;

FIG. 8 is a screen shot of the configurable adapter set up screen ofFIG. 4 when a platform field is selected, in accordance with anembodiment;

FIG. 9 is a screen shot of the configurable adapter set up screen ofFIG. 4 when an application field is selected, in accordance with anembodiment;

FIG. 10 is a screenshot of a table selection window that opens when atable field is selected from the configurable adapter set up screen ofFIG. 4, in accordance with an embodiment;

FIG. 11 is a screen shot of the configurable adapter set up screen ofFIG. 4 when a map from field is selected, in accordance with anembodiment;

FIG. 12 is a screenshot of the configurable adapter set up screen ofFIG. 4 when a destination tab is selected, in accordance with anembodiment;

FIG. 13 is a screen shot of the configurable adapter set up screen 400of FIG. 12 when a destination platform field is selected, in accordancewith an embodiment;

FIG. 14 is a screen shot of the configurable adapter set up screen ofFIG. 12 when a destination application field is selected, in accordancewith an embodiment;

FIG. 15 is a screen shot of the configurable adapter set up screen ofFIG. 12 when a map to field is selected, in accordance with anembodiment;

FIG. 16 is a screenshot of the configurable adapter set up screen ofFIG. 4 when a middleware tab is selected, in accordance with anembodiment;

FIG. 17 is a screen shot of the configurable adapter set up screen ofFIG. 16 when an adapter/messaging type field is selected, in accordancewith an embodiment;

FIG. 18 is a screen shot of the configurable adapter set up screen ofFIG. 16 when an infrastructure field is selected, in accordance with anembodiment;

FIG. 19 is a screen shot of the configurable adapter set up screen ofFIG. 16 when an approvals tab is selected, in accordance with anembodiment;

FIG. 20 is a screen shot of the configurable adapter set up screen ofFIG. 16 when an events tab is selected, in accordance with anembodiment;

FIG. 21 is a screen shot of the configurable adapter set up screen ofFIG. 16 when a task activities tab is selected, in accordance with anembodiment;

FIG. 22 is a flowchart of a process for using configurable adapters toexchange data between platforms via middleware, in accordance with anembodiment;

FIG. 23 is a schematic of a framework for purchasing products and/orservices, in accordance with an embodiment;

FIG. 24 is a schematic illustrating how analytics may be used to filter,sort, or otherwise clean up data pulled or received by an Offer APIand/or a Deal Hub component of the framework of FIG. 23, in accordancewith an embodiment;

FIG. 25 is an embodiment of a table of data provided to a productcatalog of the framework of FIG. 23, in accordance with an embodiment;and

FIG. 26 is a flow chart of a process for populating, operating, andmaintaining, a shopping interface for an organization utilizing theframework of FIG. 23, in accordance with an embodiment;

DETAILED DESCRIPTION

One or more specific embodiments will be described below. In an effortto provide a concise description of these embodiments, not all featuresof an actual implementation are described in the specification. Itshould be appreciated that in the development of any such actualimplementation, as in any engineering or design project, numerousimplementation-specific decisions must be made to achieve thedevelopers' specific goals, such as compliance with system-related andenterprise-related constraints, which may vary from one implementationto another. Moreover, it should be appreciated that such a developmenteffort might be complex and time consuming, but would nevertheless be aroutine undertaking of design, fabrication, and manufacture for those ofordinary skill having the benefit of this disclosure.

An Information Technology (IT) network of an enterprise may include anumber of computing devices, server systems, databases, and the likethat generate, collect, store, and distribute information in the normaloperations of an enterprise or organization. The enterprise may utilizedifferent platforms, applications, and/or software packages to performdifferent functions (e.g., human resources, pay roll, purchasing, assetprocurement, information technology, accounting, tax, etc.). Some ofthese platforms, applications, and/or software packages may be providedby different vendors such that the platforms, applications, and/orsoftware packages may not be set up to share data with one another.Accordingly, the enterprise may enlist a developer to write scripts(e.g., modules of software code) to facilitate the sharing of databetween platforms, applications, and/or software packages. However, asthe platforms, applications, and/or software packages are updated, thescripts may need to be correspondingly updated to ensure smoothcommunication of data between platforms. Configurable adapters that areset up by a user via a graphical user interface, as opposed to writing ascript, may be used to control a middleware instance to facilitate thesharing of data between two or more platforms, applications, and/orsoftware packages without writing or editing a script. Accordingly,configurable adapters and middleware instances may be used to build uplarge, complex frameworks of platforms, applications, and/or softwarepackages capable of performing complex tasks for the enterprise.

By way of introduction, FIG. 1 is a block diagram of a distributedcomputing system 100 that utilizes a distributed computing framework,which may perform one or more of the techniques described herein. Asillustrated in FIG. 1, one or more clients 102 communicate with aplatform 104 (e.g., a cloud service platform) over a communicationchannel 106. As shown, each client 102 may include any suitablecomputing system, such as a mobile phone, a tablet computer, a laptopcomputer, a notebook computer, a desktop computer, or any other suitablecomputing device or combination of computing devices. Each client 102may include client multiple application programs capable of running onthe computing devices. The client 102 can be implemented using a singlephysical unit or a combination of physical units (e.g., distributedcomputing) running one or more client application programs. Furthermore,in some embodiments, a single physical unit (e.g., server) may runmultiple client application programs simultaneously.

The platform 104 may include any suitable number of computing devices(e.g., computers) in one or more locations that are connected togetherand communicate using one or more networks. For instance, the platform104 may be a cloud service platform that includes various computersacting as servers in datacenters at one or more geographic locationswhere the computers are connected together using network and/or Internetconnections. The communication channel 106 may include any suitablecommunication mechanism for electronic communication between the client102 and the platform 104. The communication channel 106 may incorporatelocal area networks (LANs), wide area networks (WANs), virtual privatenetworks (VPNs), cellular networks (e.g., long term evolution networks),and/or other network types for transferring data between the client 102and the platform 104. For example, the communication channel 106 mayinclude an Internet connection when the client 102 is not on a localnetwork common with the platform 104. Additionally or alternatively, thecommunication channel 106 may include network connection sections whenthe client and the platform 104 are on different networks or entirelyusing network connections when the client 102 and the platform 104 sharea common network. Although only a few clients 102 are shown connected tothe platform 104, it should be noted that the platform 104 may connectto many clients 102 (e.g., tens, hundreds, or thousands of clients).

Through the platform 104, the client 102 may connect to various deviceswith various functionalities, such as gateways, routers, load balancers,databases, application servers running application programs on one ormore nodes, or other devices that may be accessed via the platform 104.For example, the client 102 may connect to application servers 107and/or databases 108 via the platform 104. The application servers 107may include any computing system, such as a desktop computer, laptopcomputer, server computer, and/or any other computing device capable ofproviding functionality from an application program to the client 102.The application server 107 may include one or more application nodesrunning application programs whose functionality is provided to theclient via the platform 104.

The platform 104 may include one or more database servers. The databaseservers are configured to store, manage, or otherwise provide data fordelivering services to the client 102 over the communication channel106. A database server may include one or more databases (e.g., DB 108)that are accessible by the application server 107, the client 102,and/or other devices external to the databases. The databases may beimplemented and/or managed using any suitable implementations, such as arelational database management system (RDBMS), an object database, anextensible markup language (XML) database, a configuration managementdatabase (DB), a management information base (MIB), one or more flatfiles, and/or or other suitable non-transient storage structures. Insome embodiments, more than a single database server may be utilized.Furthermore, in some embodiments, the platform 104 may have access toone or more databases external to the platform 104 entirely, such as ata client site.

In the depicted topology, access to the platform 104 is enabled via amanagement, instrumentation, and discovery (MID) server 126 via acommunication channel 128, such as an External Communications Channel(ECC) Queue. The MID server 126 may include an application program(e.g., Java application) that runs as a service (e.g., Windows serviceor UNIX daemon) that facilitates communication and movement of databetween the platform 104 and external applications, data sources, and/orservices. The MID server 126 may be executed using a computing device(e.g., server or computer) on the network 112 that communicates with theplatform 104. As such, in some embodiments, the MID server 126 mayconnect back to the platform 104 using a virtual private networkconnection that simulates the configuration items (CIs) being connectedto the platform 104 on a common physical network.

The communication channel 128 may be a database table that is typicallyqueried, updated, and inserted into by other systems. Each record in thecommunication channel 128 is a message from an instance in the platform104 to a system (e.g., MID server 126) external to the platform 104 thatconnects to the platform 104 or a specific instance running in theplatform 104 or a message to the instance from the external system. Thefields of a communication channel 128 record include various data aboutthe external system or the message in the record. For example, therecord may include an agent field, a topic field, a name field, a sourcefield, a response to field, a queue field, a state field, a created timefield, a processed time field, a sequence number for the message, anerror string field, a payload field, and/or other suitable fields foridentifying messages and/or the systems sending/receiving the message.

Although the system 100 is described as having the application servers107, the DB 108, the communication channel 128, the MID server 126, andthe like, it should be noted that the embodiments disclosed herein arenot limited to the components described as being part of the system 100.Indeed, the components depicted in FIG. 1 are merely provided as examplecomponents and the system 100 should not be limited to the componentsdescribed herein. Instead, it should be noted that other types of serversystems may communicate with the platform 104 in addition to the MIDserver 126.

Further, it should be noted that server systems described herein maycommunicate with each other via a number of suitable communicationprotocols, such as via wired communication networks, wirelesscommunication networks, and the like. In the same manner, the client 102may communicate with a number of server systems via a suitablecommunication network without interfacing its communication via theplatform 104.

In any case, to perform one or more of the operations described herein,the client 102, the application server 107, the MID server 126, andother server or computing system described herein may include one ormore of the computer components depicted in FIG. 2. FIG. 2 generallyillustrates a block diagram of example components of a computing device200 and their potential interconnections or communication paths, such asalong one or more busses. As briefly mentioned above, the computingdevice 200 may be an embodiment of the client 102, the applicationserver 107, a database server (e.g., DB 108), other servers in theplatform 104 (e.g., server hosting the communication channel 128), adevice running the MID server 126, and/or any of the CIs. As previouslynoted, these devices may include a computing system that includesmultiple computing devices and/or a single computing device, such as amobile phone, a tablet computer, a laptop computer, a notebook computer,a desktop computer, a server computer, and/or other suitable computingdevices.

As illustrated, the computing device 200 may include various hardwarecomponents. For example, the device includes one or more processors 202,one or more busses 204, memory 206, input structures 208, a power source210, a network interface 212, a user interface 214, and/or othercomputer components useful in performing the functions described herein.

The one or more processors 202 may include a processor capable ofperforming instructions stored in the memory 206. For example, the oneor more processors may include microprocessors, system on a chips(SoCs), or any other suitable circuitry performing functions byexecuting instructions stored in the memory 206 or in an otherwiseaccessible location. Additionally or alternatively, the one or moreprocessors 202 may include application-specific integrated circuits(ASICs), field-programmable gate arrays (FPGAs), and/or other devicesdesigned to perform some or all of the functions discussed hereinwithout calling instructions from the memory 206. Moreover, thefunctions of the one or more processors 202 may be distributed acrossmultiple processors in a single physical device or in multipleprocessors in more than one physical device. The one or more processors202 may also include specialized processors, such as a graphicsprocessing unit (GPU).

The one or more busses 204 include suitable electrical channels toprovide data and/or power between the various components of thecomputing device. For example, the one or more busses 204 may include apower bus from the power source 210 to the various components of thecomputing device. Additionally, in some embodiments, the one or morebusses 204 may include a dedicated bus among the one or more processors202 and/or the memory 206.

The memory 206 may include any tangible, non-transitory, andcomputer-readable storage media. For example, the memory 206 may includevolatile memory, non-volatile memory, or any combination thereof. Forinstance, the memory 206 may include read-only memory (ROM), randomlyaccessible memory (RAM), disk drives, solid state drives, external flashmemory, or any combination thereof. Although shown as a single block inFIG. 2, the memory 206 can be implemented using multiple physical unitsof the same or different types in one or more physical locations. Theone or more processor 202 may access data in the memory 206 via the oneor more busses 204.

The input structures 208 provide structures to input data and/orcommands to the one or more processor 202. For example, the inputstructures 208 include a positional input device, such as a mouse,touchpad, touchscreen, and/or the like. The input structures 208 mayalso include a manual input, such as a keyboard and the like. Theseinput structures 208 may be used to input data and/or commands to theone or more processors 202 via the one or more busses 204. The inputstructures 208 may alternatively or additionally include other inputdevices. For example, the input structures 208 may include sensors ordetectors that monitor the computing device 200 or an environment aroundthe computing device 200. For example, a computing device 200 cancontain a geospatial device, such as a global positioning system (GPS)location unit.

The power source 210 can be any suitable source for power of the variouscomponents of the computing device 200. For example, the power source210 may include line power and/or a battery source to provide power tothe various components of the computing device 200 via the one or morebusses 204.

The network interface 212 is also coupled to the processor 202 via theone or more busses 204. The network interface 212 includes one or moretransceivers capable of communicating with other devices over one ormore networks (e.g., the communication channel 106). The networkinterface may provide a wired network interface, such as Ethernet, or awireless network interface, such an 802.11, Bluetooth, cellular (e.g.,LTE), or other wireless connections. Moreover, the computing device 200may communicate with other devices via the network interface 212 usingone or more network protocols, such as Transmission ControlProtocol/Internet Protocol (TCP/IP), power line communication (PLC),WiFi, infrared, and/or other suitable protocols.

A user interface 214 may include a display that is configured to displayimages transferred to it from the one or more processors 202. Inaddition and/or alternative to the display, the user interface 214 mayinclude other devices for interfacing with a user.

FIG. 3 is a block diagram of an embodiment of a system 300 forexchanging data between platforms 302, 304. The system 300 mayimplemented, for example, within the distributed computing system ofFIG. 1. As previously described, an enterprise may utilize multipledifferent platforms 302, 304 in order to run the enterprise moreefficiently. For example, the enterprise may use platform A 302 forfinancial record keeping, and use platform B as a human resources (HR)web portal for employees to access email, manage health benefits, 401(k)contributions, etc. For the sake of clarity and simplicity, only twoplatforms 302, 304 are shown in FIG. 3, however, it should be understoodthat an enterprise may utilize many more platforms in the operation oftheir enterprise. Each platform 302, 304 may include one or more DBs306, 308, which may store one or more tables. In some cases, it may bebeneficial to share data between platforms 302, 304. For example, in theabove example, platform A 302 may wish to pull data from platform Bregarding how much was paid out to employees via payroll and how muchwas spent on health benefits and 401(k) contributions. In such anembodiment, one or more middleware instances 310 (e.g., middlewarecomponents) may act as an interface between the platforms 302, 304,locating the desired data within the source DB 308, copying the datafrom the source DB 308, in some cases reformatting the data, and pushingthe data to the destination DB 306. The data may then be used byplatform A 302 to generate financial reports, or otherwise performfinancial analysis.

Typically, the middleware 310 is configured via a script or some otherpiece(s) of code. The script may be written by an in-house developer orIT specialist, or the script writing may be outsourced to an outsidedeveloper (e.g., a contractor or a software development servicescompany). In addition to requiring specialized knowledge of softwarecode, writing the script consumes resources that the enterprise couldreallocate to other tasks. Enterprises around the world may devoteresources to writing similar scripts to perform the same or similartasks, resulting in redundancies and inefficiencies. Further, as theplatforms update and evolve over time, the scripts will need to beupdated accordingly, or risk not working properly, if at all.

In the illustrated embodiment, one or more configurable adapters 312 maybe used to configure the middleware 310, eliminating the need for ascript. Accordingly, the configurable adapters 312 enable a personwithout the specialized knowledge of software development to configurethe middleware 310. The configurable adapters 312 may be accessible viaa user interface (e.g., via a web browser or an application) of acomputing device (e.g., one of the clients shown in FIG. 1).

In some embodiments the configurable adapters 312 may be incommunication with a machine learning component, such as DX Continuum(DX) 314. The DX 314 may be stored in the cloud (e.g., a distributedcomputing system), on a remote server, or on an on-premises server (“onprem”). The DX 314 may collect data from multiple customers over timeand utilize machine learning (e.g., a trained neural network) to developa library of rules and/or combinations of adapters, platforms 302, 304,middleware 310, and/or infrastructure combinations. As a user is usingthe configurable adapters 312 to configure the platforms 302, 304 andmiddleware 310 combinations, the DX 314 may make suggestions as to howthe user should set the system up, or approve a configuration that theuser has set up.

A user may set up the configurable adapters 312 via the user interfaceof a computing device, such as a desktop computer, a laptop computer, anotebook computer, a tablet computer, a mobile phone, or some othercomputing device. FIG. 4 is a screen capture from a configurable adapterset up screen 400. As shown, the configurable adapter set up screen 400includes a top window 402 that includes various informationcorresponding to the configurable adapter. For example, in theillustrated embodiment, the top window 402 includes fields forconfigurable adapter number 404, priority 406, impact 408, expectedstart date and time 410 expected end data and time 412, state 414,frequency 416, and data override 418. In some embodiments, the topwindow 402 may include a check box to indicate whether or not theconfigurable adapter is active.

A row of tabs, including a data source tab 420, a destination tab 422, amiddleware tab 424, and an approvals tab 426 control what is displayedin a middle window 428. When the data source tab 420 is selected, thefields displayed in the middle window 428 may include, for example,source platform 430, source platform new URL 432, source application434, source application URL 436, authentication use name 438,authentication password 440, source table 442, and source map from field444. The fields displayed when other tabs are selected are describedbelow.

Another row of tabs, including an approvers tab 446, an events tab 448,and a task activities tab 450 control what is displayed in a bottomwindow 452. In the illustrated embodiment, the approvers tab 446 isselected, so the bottom window shows that approval has been requestedfor the current configurable adapter and is currently pending.

Returning to the configurable adapter number field 404, in the topwindow 402, the configurable adapter number is entered by the user. Theconfigurable adapter number may be, for example, an alpha-numericcharacter string that corresponds to the configurable adapter.

In the illustrated embodiment, the priority field 406 is filled byselecting an option from a drop-down menu. FIG. 5 is a screen shot ofthe configurable adapter set up screen 400 of FIG. 4 when the priorityfield 406 is selected. As shown, the user may select from options of“None”, “1—Critical”, “2—High”, “3—Moderate”, “4—Low”, and “5—planning”.In some embodiments, times of limited resources (e.g., bandwidth), dataexchanges may be prioritized based on a designated priority of theoperations.

FIG. 6 is a screen shot of the configurable adapter set up screen 400 ofFIG. 4 when the impact field 408 is selected. The impact field 408 isfilled by selecting an option from a drop-down menu. As shown, the usermay select from options of “1—High”, “2—Medium”, and “3—Low”.

Returning to FIG. 4, the expected start field 410 and expected end field412 may be filled in be the user. The expected start field 410 mayspecify, for example the date and time of the first data exchange. Theexpected end field 412 may specify, for example the date and time thatthe data exchange stops, or for the date and time of the last exchange.For each field 410, 412, the user may manually fill in a date and time,or selecting the field may cause a window to open that allows the userto cycle through a calendar and/or clock to select start and end datesand times.

The state field 414 is filled by selecting an option from a drop-downmenu. FIG. 7 is a screen shot of the configurable adapter set up screen400 of FIG. 4 when the state field 414 is selected. As shown, the usermay select from options of “Pending”, “Open”, “Work in Progress”,“Closed Complete”, “Closed Incomplete”, and “Closed Skipped”. “Pending”indicates that the configurable adapter has been set up, but is pendingapproval. “Open” indicates that the configurable adapter has been setup, approved, and is being used. “Work in Progress” indicates that theconfigurable adapter is in the process of being set up. “ClosedComplete” indicates that the configurable adapter has been set up,approved, that the expected end date has passed, and that theconfigurable adapter's operations have been successfully completed.“Closed Incomplete” indicates that the configurable adapter was set up,approved, and attempted to exchange data, but was unable to complete thedata exchange. “Closed Skipped” indicates that the configurable adapterwas set up, and approved, but for some reason was unable to start thedata exchange, so the data exchange was skipped.

Returning to FIG. 4, the frequency field 416 is filled by selecting anoption from a drop-down menu. The options may include, for example,hourly, daily, weekly, monthly, quarterly, annually, etc. In someembodiments, the use may select an “other” option and enter a frequencyoption that is not in the drop down menu (e.g., every three days, everytwo weeks, etc.).

The data override field 418 is also filled by selecting an option from adrop-down menu. The options for the data override field are simply “yes”and “no”. If “yes” is selected, the data from the source table willoverride the data in the same field of the destination table. If “no” isselected, the data from the source table will be copied to thedestination table by creating an adjacent duplicate field with the newdata. In other embodiments, data override may be specified by othermeans, such as a check box.

Transitioning now to the middle window 428, as previously discussed,because the data source tab 420 is selected, the middle window 428displays information corresponding to the source of the data. Theplatform field 430 is filled by selecting an option from a drop-downmenu. FIG. 8 is a screen shot of the configurable adapter set up screen400 of FIG. 4 when the platform field 430 is selected. As shown, theuser may select from options of ANAPLAN®, ORACLE FUSION®, SAP®,WORKDAY®, SERVICENOW®, and PEOPLESOFT®. It should be understood,however, that other platforms may be available. Returning to FIG. 4,once the platform field 430 is selected, the new platform URL field 432is filled in. The new platform URL field 432 may be manually completedby the user, or automatically filled in.

FIG. 9 is a screen shot of the configurable adapter set up screen 400 ofFIG. 4 when the application field 434 is selected. The application field434 is filled by selecting an option from a drop-down menu. As shown,the user may select from options of “Finance”, “IT”, “Marketing”,“Sales”, “Supply Chain”, “CRM”, “Financials”, “Asset Accounting”,“FI/CO”, “MM”, “Asset”, “Procurement”, “Product Catalog”, etc. However,it should be understood that application options may be dependent uponthe selected platform. Returning to FIG. 4, once the application field434 is selected, the new application URL field 436 is filled in. As withthe new platform URL field 432, the new application URL field 436 may bemanually completed by the user, or automatically filled in.

Once the platform field 430 and application field 434 have been filledin, the user manually enters his or her username and password for thesource application into the respective username and password fields 438,440. In other embodiments, the user may provide biometric information(e.g., fingerprint, retina, facial data, voice data, etc.) asauthentication or use other suitable authentication criteria. To fill inthe table field 442, the user selects the table field 442, which causesa table selection window to open. FIG. 10 is a screenshot of the tableselection window 500 that opens when the user selects the table field.As shown, the table selection window 500 includes a listing of multiplepossible tables. Upon the user's selection of one of the listed tables,the table window may close and the name of the selected table may belisted in the table field. Once a table has been selected, the user mayfill in the map field. FIG. 11 is a screen shot of the configurableadapter set up screen 400 of FIG. 4 when the map from field 444 isselected. In the illustrated embodiments, the options for the map fromfield 444 include “acquisition cost (local currency)”, “acquisition cost(USD)”, “NBV (local currency”, and “NBV(USD)” because these are fieldsfrom the selected table, “*BOW-IBM”. However, if a different table isselected, the options for the map from field 444 will correspond to thefields of the selected table. The map from field 444 is the field fromwhich data will be pulled and pushed to the destination location.

When the destination tab 422 is selected, the middle window 428 ispopulated with information corresponding to the destination of theinformation. FIG. 12 is a screenshot of the configurable adapter set upscreen 400 of FIG. 4 when the destination tab 422 is selected. As thename suggests, the destination is the location to which data pushed orpulled from the data source is directed. As shown, when the destinationtab 422 is selected, the fields displayed in the middle window 428 mayinclude, for example, destination platform 600, destination application602, authentication use name 604, authentication password 606,destination table 608, and source map to field 610.

The destination platform field 600 is filled by selecting an option froma drop-down menu. FIG. 13 is a screen shot of the configurable adapterset up screen 400 of FIG. 12 when the destination platform field 600 isselected. As shown, the user may select from options of ANAPLAN®, ORACLEFUSION®, SAP®, WORKDAY®, SERVICENOW®, and PEOPLESOFT®. It should beunderstood, however, that other platforms may be available.

FIG. 14 is a screen shot of the configurable adapter set up screen 400of FIG. 12 when the destination application field 602 is selected. Thedestination application field 602 is filled by selecting an option froma drop-down menu. As shown, the user may select from options of“Finance”, “IT”, “Marketing”, “Sales”, “Supply Chain”, “CRM”,“Financials”, “Asset Accounting”, “FI/CO”, “MM”, “Asset”, “Procurement”,“Product Catalog”, etc. However, the applications options may bedependent upon the platform selected. Returning to FIG. 12, once thedestination application field 602 is selected, the user manually entershis or her username and password for the destination application intothe respective username and password fields 604, 606. To fill in thedestination table field 608, the user selects the destination tablefield 608, which causes the table selection window 500 to open, aspreviously shown and described with regard to FIG. 10. Upon the user'sselection of one of the listed tables, the table window may close andthe name of the selected table may be listed in the table field. Once atable has been selected, the user may fill in the map to field 610. FIG.15 is a screen shot of the configurable adapter set up screen 400 ofFIG. 12 when the map to field 610 is selected. In the illustratedembodiments, the options for the map to field 610 include “NBV (localcurrency)”, “NBV (USD)”, “Total Cost (local currency”, and “Total Cost(USD)” because these are fields from the selected destination table,“*BOW-IBM”. However, if a different table is selected, the options forthe map to field 610 will correspond to the fields of the selectedtable. The map to field 602 is the field to which data from the sourcelocation will be pulled and/or pushed.

When the middleware tab 424 is selected, the middle window 428 ispopulated with information corresponding to the middleware used to pulland/or push data from the source to the destination. FIG. 16 is ascreenshot of the configurable adapter set up screen 400 of FIG. 4 whenthe middleware tab 424 is selected. As shown, when the middleware tab424 is selected, the fields displayed in the middle window 428 mayinclude, for example, adapter/messaging type 700, infrastructure 702,URL 704, status 706, and DX recommended 708.

The adapter/messaging type field 700 is filled by selecting an optionfrom a drop-down menu. FIG. 17 is a screen shot of the configurableadapter set up screen 400 of FIG. 16 when the adapter/messaging typefield 700 is selected. As shown, the user may select from options ofJSON, MID Server, MULESOFT®, REST, and SOAP. It should be understood,however, that other middleware options may be available. Middleware maybe leveraged to transport data across platforms and can be hosted in thecloud on a server on the premises (“on prem”). In some embodiments, themiddleware may be automatically selected, or a recommended middlewaremay be pre-selected.

FIG. 18 is a screen shot of the configurable adapter set up screen 400of FIG. 16 when the infrastructure field 702 is selected. Theinfrastructure field 702 is filled by selecting an option from adrop-down menu. As shown, the user may select “Cloud”, or “On Prem”.Selecting “Cloud” indicates that the middleware is running on acloud-based server. Selecting “On Prem” indicates that the middleware isrunning on a local, on premises, server.

Returning to FIG. 16, once the adapter/messaging type and infrastructurefields have been filled in, user manually enters the URL of themiddleware into the middleware URL field 704. As shown, the status field706 and DX recommended field 708 are represented by check boxes. Theuser checks the status field 706 if the middleware is operational andleaves the status field 706 checkbox blank if the middleware is notoperational. Similarly, the DX recommended field 708 check box ischecked if the adapter/infrastructure is recommended by the DX and leftunchecked if adapter/infrastructure is not recommended by the DX.

FIG. 19 is a screen shot of the configurable adapter set up screen 400of FIG. 16 when the approvals tab 426 is selected. When the Approvalstab 426 is selected, the middle window 428 displays an approvals setfield 800 that shows the date and time that approvals were set or willbe set. The approvals set field 800 may be auto-filled based on whenapprovals were requested and approved.

When the approvers tab 446 is selected, the bottom window 452 displaysthe people who approve the configurable adapters. As shown, a table maybe displayed with a record for each approver. The record may include,for example, the approvers name, the status of the approval request(requested, approved, denied, etc.), any comments provided by theapprover or the requester, and a date/time that the request was created.A user may use this portion of the configurable adapter set up screen400 to add new approvers, remove approvers, or edit existing approvers.

FIG. 20 shows the configurable adapter set up screen 400 of FIG. 16 whenthe events tab 448 is selected. Events are messages generated by networkmanagement and/or maintenance systems communicating errors, warnings,status updates, or suggestions. In some embodiments, the user may set upspecific triggering events to generate an event that shows up in thebottom window. Though no events are shown in FIG. 20, when messages arereceived, records corresponding to the error or warning messages may bedisplayed in the bottom window 452. Such records may include, forexample, the date and time created, the corresponding agent, the source,the component, the type, the severity, the name, etc. If the listedevents are suggestions, the user may accept or reject the suggestions.

FIG. 21 shows the configurable adapter set up screen 400 of FIG. 16 whenthe task activities tab 450 is selected. Task activities may includespecific instances in which data is pulled from a source and pushed to adestination and/or when the configurable adapter is updated orconfigured. Though no task activities are shown in FIG. 21, when theconfigurable adapter pulls data from a source and provides it to adestination, a record may be created and displayed in the bottom window452. The record may include, for example, task number, task type, thesource, the destination, information about the data, etc.

FIG. 22 is a flowchart of a process 900 for using configurable adaptersto exchange data between platforms via middleware. In block 902, a userprovides information via a graphical user interface about the source ofthe data to be exchanged. As shown and described with regard to FIGS.8-11, this may include, for example, information about the sourceplatform, the source application, a username and password for the sourceapplication, a table and field in which the data is stored, etc. Inblock 904, the user provides information via the graphical userinterface about the destination of the data to be exchanged. As shownand described with regard to FIGS. 12-15, this may include, for example,information about the destination platform, the destination application,a username and password for the destination application, a table andfield in which the data is to be stored, etc.

In some embodiments, the DX 314 may suggest a specific middleware basedon the source and/or the destination. This recommendation may be basedfor example, on historical data collected from customers over time. Inblock 908, the user provides information via the graphical userinterface about the middleware used to exchange the data. As shown anddescribed with regard to FIGS. 16-18, this may include, for example, theadapter and/or messaging type of the middleware, whether the middlewareis cloud-based or on-premises, the URL of the middleware, the status ofthe middleware, whether the middleware is recommended by the DX 314,etc. If middleware is suggested in block 906, the user may accept thesuggestion and use the suggested middleware, or reject the suggestionand specify a different middleware. At block 910 approvals, if any, maybe requested from those with approval power.

At block 912, the middleware retrieves the data from the data source andcopies the data to the destination. The data exchange may be prompted bya request from a user (e.g., on demand), upon the expiration of a timer,at regularly scheduled intervals, upon the occurrence of some triggeringevent (e.g., source data is updated, etc.). In some embodiments, atblock 914, information may be collected about the data exchange (e.g.,was the data exchange successful, how long did the data exchange take,etc.) and provided to the DX 314 for storage in an exchange informationlog. As previously discussed, the DX may collect data from manycustomers and use machine learning techniques to analyze the datacollected over time to make recommendations about configurations andgenerally improve the performance of data exchanges between platforms.

Configurable adapters may be set up to facilitate the exchange of databetween platforms without a user or developer writing scripts tofacilitate the desired data exchange. As such, the configurable adaptersdisclosed herein may allow for the development of a framework havingmany platforms and/or applications in communication with one another toperform complex tasks. FIG. 23 is a schematic of a framework 1000 forpurchasing. As shown, a product listing 1002 is generated based onproducts available from one or more vendors 1004. A product model API1006 extracts and updates product model data for the products listed inthe product listing 1002. As shown, the product model data may include,for example, manufacturer part number or UPC, model name, productdescription, vendor, vendor part number, unit price, country/region,managed by, model category, compatible products, substitute products,image and/or icon, department, lead time, in-stock or out of stock, etc.In some embodiments, the primary key for the product data is themanufacturer part number and/or the UPC. The product model API 1006 mayupdate regularly (e.g., every Saturday) to ensure that all relevantfields for existing products are up to date and any new product modelshave been added. The product model API 1006 may also be configured toupdate on demand based on a command from a catalog administrator. If anupdate or addition of new product fails, the status code will becaptured, reviewed by the catalog administrator and added. When newproducts are added, an approval task will be sent to the catalogadministrator for approval. Once approved, the product will be availablefor users to purchase.

An offer API 1010 pulls or receives data from the vendors 1004corresponding to various promotional offers from the vendors 1004 forone or more of the products collected by the product model API 1006. Aswith the product model API 1006, the primary data key is themanufacturer part number and/or UPC and the vendor ID of the vendoroffering the promotional offer. The offer API 1010 updates on a regularschedule (e.g., every 12 hours), but an update can be initiatedon-demand by the catalog administrator. The offer API 1010 may collectand store data corresponding to the vender ID, offer ID, unit price, thecurrent promotional offer price, offer validity, previous promotionaloffer prices. The promotional information will be retained while theoffer is valid (i.e., until the offer expires). Upon expiration of theoffer, the displayed price may return to the normal unit price. Allpurchase orders created for items with a promotional offer may includean offer identification number and offer price for respectiveperformance linked incentives. The offer identification number, and insome cases, other offer data will be available on both purchaserequisition and purchase order line items. When new offers are added,review tasks will be created for the catalog administrator to review thenew offers.

The offer API routes promotional offer details to a deal hub 1012. Thedeal hub 1012 acts as a transactional repository of all offers (currentor expired) that have been offered by vendors 1004 via the offer API1010. In some embodiments, only select users will have access to thedeal hub 1012. The deal hub may display data related to an offer, suchas vender name, deal source, offer ID, validity, unit price, currency,region, product model name, category, etc. Active deals with the lowestoffer price for each vender will be displayed to the user with thevendor catalog item that corresponds to the product model. The offerwill only display if the offer is valid. If there is no valid offer, theoffer category will display as null. Further, if the deal is active, itmay be flagged as “active” or otherwise emphasized/highlighted. Uponexpiration of an offer, the offer will no longer be displayed to theuser, but offer information will be saved and stored for future analysisand reference. In some embodiments, some users (e.g., catalogadministrator or strategic sourcing team) may have the authority tocreate an offer manually. Further, some users may have the authority torequest a quote from a vendor.

In some embodiments, the framework 1000 may also include a price checkAPI that checks for lower prices than what is available in the catalog.In such embodiments, the price check API may be a dynamic API that runsbehind the scenes to validate price information on an in-flight purchaserequisition by querying manufacturer part number and/or UPC onperformance linked incentives. When the manufacturer part number and/orUPC is successfully validated on active performance linked incentives,the price check API calls associated endpoints to validate whether ornot there are lower prices (e.g., better promotional offers) to be takenadvantage of. Accordingly, the price check API may be utilized to catchprice reductions or competing offers on a vendor's platform. Ifcompeting price points exist, the lowest priced option will be updatedto the catalog item as the unit price. The performance linked incentiveswill also be updated accordingly. The new lower price will exist as thenew default unit price until the price is updated by the vendor.

Information from the product model API 1006 and the offer API 1010 (viathe deal hub 1012) may be combined to create a vendor catalog item 1008for each product available for purchase. The various catalog items 1008combine to form a product catalog 1014. The product catalog 1014 isaccessible by users via a marketplace 1018 (e.g., ShopNow) with apeer-to-peer (P2P) dashboard interface that users may use to placeorders for products within the product catalog 1014. In general,products will be auto-published to ShopNow 1018, but the catalogadministrator may have the authority to publish or unpublish items via acatalog interface. Some items or categories of items may be set up torequire a catalog administrator's approval before being listed onShopNow for purchase. A scheduled job may be run at regular intervals(e.g., every hour, every 4 hours, every 6 hours, every 12 hours, once aday, etc.) to automatically publish items that are approved forpublishing, but have not published yet. However, the catalogadministrator may also have the authority to run the scheduled job uponrequest on demand. Items that have been manually removed from ShopNow1018 by the catalog administrator will be marked as “retired” and willnot be republished unless the status is updated to reinstated by thecatalog administrator.

Orders placed by users may go through a purchase requisition component1020, a financial management platform 1022, such as SAP® Financials, andthen through an order API 1024 that communicates the order to the vendor1004. A number of other integrated platforms may use order data forvarious purposes. For example, a dynamic discounting and supplierinformation and performance management platform 1026, such as SAP®ARIBA® may pull order data for analysis. Similarly, a sourcing aprocurement management platform 1028, such as SCOUT®, may pull data tosupply to a vendor hub 1030. The Vendor hub 1030 may provide data to theSAP® Financials platform 1022 and to a contract lifecycle managementplatform 1032, such as APTTUS®. Other platforms, such as, for example,TANGO® 1034, TAXWARE® 1036, etc., may also provide data to SAP®Financials 1022. For the sake of simplicity, the various platforms shownin FIG. 23 are connected by arrows, indicating communication between theplatforms. It should be understood, however, that each of thecommunication arrows should be understood to include a middlewareinstance driven by one or more configurable adapters, as shown anddescribed in FIG. 3.

Once the vendor 1004 ships the product, data may be provided to ashipment API 1038 that provides shipping information about the shippedproduct to the product catalog 1014. The shipping information mayinclude, for example, the shipping carrier, tracking ID number, shipdate, expected delivery date, delivery date (if already delivered), andproduct information, such as tag number, serial number, MAC, etc.

FIG. 24 is a schematic illustrating how analytics may be used to filter,sort, or otherwise clean up data pulled or received by the Offer APIand/or the Deal Hub. As shown, in addition to vendors 1004, the offerAPI 1010 may pull or receive offers from, or find out about offers from,social media platforms 1100, such as FACEBOOK®, TWITTER®, PINTEREST®,etc. That is, offers for various products and/or services may be postedon a social media platform that is otherwise not pulled by the offer API1010 form the vendors 1004. The Offer API 1010 may also use one or morecoupon websites/services 1102, such as GROUPON®, FAB®, WOOT®, etc. tofind offers for products and/or services. Finally, in some embodiments,there may also be a manual mechanism 1104 for loading deals to beincorporated into the data pulled by the offer API 1010. Once offer datais pulled or received by the offer API 1010, the data may be run throughan analytics component 1106. The analytics component 1106 may beconfigured to pre-process (e.g., filter, sort, remove duplicate, etc.)data received by the offer API 1010. For example, the analyticscomponent 1106 may be configured to remove expired offers or offers thatare not yet active. The analytics component 1106 may also removeirrelevant offers. For example, based on search terms, the offer API1010 may return false positives and retrieve offers that are notactually relevant, such as returning kitchen supplies to a company thatdoes chemical processing, etc.

In other embodiments, the analytics component 1106 may retrieve an offerfrom a new vendor that is lower than offers for the same product orservice from existing vendors. In such a case, the analytics component1106 may flag the new vendor for review and approval or recommend thatthe new vendor be on-boarded. The analytics component 1106 may thenprovide the pre-processed data to the deal hub 1012. The deal hub wasshown and discussed with regard to FIG. 24.

A second analytics component 1108 may be disposed between the deal huband the product catalog 1014 to further process the offer data. Forexample, the second analytics component 1108 may be configured tocapture negative or positive impressions for products, services, and/orvendors based on posted reviews, social media posts or comments, blogs,etc. Accordingly, the second analytics component 1108 may removelistings associated with products, services, and/or vendors havingoverwhelmingly negative reviews or feedback. The second analyticscomponent 1108 may also be configured to track offer data over time andtake note of trends in the data. For example, the second analyticscomponent may notice regular (e.g., seasonal) variations in deals thatare somewhat consistent year to year, month to month, week to week, etc.Further, the second analytics component may observe that there is anideal period or periods of time in advance to buy plane tickets, reservehotel rooms or rental cars, etc. Accordingly, recommendations may bemade to the customer in the product catalog as to when the customershould make the purchase.

A user may configure the offer API 1010, the deal hub 1012, and/or theanalytics components 1106, 1108 to only provide data that the user isinterested. Alternatively, or in addition, the user may provide feedback(e.g., “show me more deals like this”, “do not show me any more dealslike this”, “do not show deals from this vender”, “do not show offersfor products or services that are poorly rated”, etc.), which the systemmay use to fine-tune the underlying algorithms. In some embodiments,machine learning may be utilized for customization of the offer API1010, the deal hub 1012, and/or the analytics components 1106, 1108based on a user's feedback or the behavior of a user (e.g., neverpurchasing items from a vendor). Additionally, machine learning may beutilized to display like products and services (e.g., substitutes) nextto or near one another. Though first and second analytics components1106, 1108 are shown in FIG. 24, it should be understood that in otherembodiments, there may be a single analytics components that performsthe described functions, or more than two analytics components 1106,1108 disposed along the data path between the vendors 1004 and theproduct catalog 1014. Further, in some embodiments, the describedfunctionality may be performed by the offer API 1010 and/or the deal hub1012.

FIG. 25 is an embodiment of a table 1200 of data provided to the productcatalog. As shown, the table includes the product information pulled orreceived by the product model API, combined with offer data pulled bythe offer API, and data pulled by or produced by the deal hub. As shown,a record is generated for each product or service offered by eachvendor. Each record is allocated a row of the table 1200. Each recordmay include data corresponding to various data fields, such as, forexample, the product or service name 1202, the product or servicecategory 1204, the manufacturer 1206, the vendor 1208, the region 1210,the offer start date 1212, the offer end date 1214, the acceptable usedate 1216 (e.g., an expected earliest date that a given purchase couldbe made considering normal lead times for quotes, final purchase price,approval, etc.), the percentage discount 1218, a rating 1220 (e.g.,according to user reviews, professional reviewers, consumer reports,etc.), an offer type 1222 (e.g., purchase, lease, subscription, service,etc.), the offer state 1224 (e.g., not yet active, active, expiringsoon, expired, etc.), the net payment term of the offer 1226, vendorstatus 1228, etc.

In some embodiments, the table 1200 may include financial data (e.g. ina financial mode or in a normal mode), such as material group, GL code,asset class, expense code, etc. Further, product models that are mappedto a model category may inherit financial data attributes associatedwith the model category. Financial data may be updated dynamically(e.g., when a new product listing is created), or automatically atregularly scheduled intervals. When financial data is updated for acategory of products and/or services, all of the products and/orservices belonging to the category may also be updated. In someembodiments, a scheduled job may run at regular intervals (e.g.,monthly, weekly, daily, etc.) during times of low traffic (e.g., nights,weekends, etc.) to ensure that all listed product models conform toprescribed data attribute assignments. Anomalies may be automaticallyfixed or trigger the creation of an alert. In some embodiments, thescheduled job may also be run on-demand upon request of the catalogadministrator or another user with authority.

In some embodiments, the data may be sortable by some or all of thelisted data fields. It should be understood, however, that a record maynot include data for all listed fields. For example, some of the listedproducts do not include an acceptable use date. In such instances, novalue may be displayed, or a place holder (e.g., “n/a”) indicating thatno data is available. Further, it should be understood that data may becollected and/or displayed beyond what is shown in table 1200. Withinthe product catalog, the data may be displayed to the user in a similarfashion as shown in FIG. 25, or the data may be provided to a userinterface that organizes and displays the data in other formats,including a format configured by the user.

Returning to FIG. 23, in some embodiments, ShopNow 1018 and/or thepurchase requisition component 1020 may automate or semi-automatepurchasing. For example, in some embodiments, purchases of productsand/or services may occur at regular intervals (e.g., annually,quarterly, monthly, weekly, etc.), or when an amount of a product dipsbelow some threshold value. In such an embodiment, a purchase requestmay be automatically created. The purchase request may be sent to adesignated person for approval and then sent out to the vendor. In otherembodiments, some purchases may have a blanket approval (e.g., for aspecific purchase and/or below a specified price). In other embodiments,the deal hub 1012 may automatically generate an alert or generate apurchase request when an offer is received for a specified productoffering a product below a specified price or at a percentage discountabove some threshold amount, purchasing a specified about of a productor service. Upon approval, if not already done, a purchase request maybe generated and sent out for approval. A purchase order may then besent out to the vendor.

FIG. 26 is a flow chart of a process 1300 for populating, operating, andmaintaining, a shopping interface for an organization. In block 1302product/service data is pulled or received (e.g., by a product modelAPI). As shown and discussed with regard to FIGS. 23 and 24, theproduct/service data may be pulled directly form one or more vendors,from one or more social media platforms, from one or more couponservices, from one or more manual mechanisms for loading deals, or fromother sources. The product model data may include, for example,manufacturer part number or UPC, model name, product description,vendor, vendor part number, unit price, country/region, managed by,model category, compatible products, substitute products, image and/oricon, department, lead time, in-stock or out of stock, etc. In someembodiments, the primary key for the product data is the manufacturerpart number and/or the UPC.

In block 1304, offer data is pulled or received for one or more of theproducts corresponding to one or more promotional offers for theproducts in question. The offer data may include, for example, to thevender ID, offer ID, unit price, the current promotional offer price,offer validity, previous promotional offer prices, etc.

At block 1306, the product/service and/or offer data may be analyzed. Asdiscussed with regard to FIG. 24, processing may include, for example,filtering data, sorting data, removing duplicate records, removingexpired offers or offers that are not yet active, removing offers forirrelevant products, flagging offers from vendors that are not in thesystem, organizing reviews and/or feedback for products, track and/orchanges in offers over time, forecast likely changes in offers based onhistorical data, implement user configurations and/or preferences, etc.

At block 1308, the analyzed product model and offer data for a productare combined to generate a catalog item. At block 1310 the catalog itemis listed (e.g., displayed within a graphical user interface) in thecatalog for users to view and purchase. At decision 1312, the process1300 determines whether an update job should be performed. Update jobsmay be performed at regular intervals (hourly, daily, weekly, monthly,quarterly, etc.), or on demand at the request of the catalogadministrator. If it is time for a regularly scheduled update job, or anupdate job has been requested, the process 1300 returns to block 1302and begins pulling product/service data to update the catalog. If it isnot time for a regularly scheduled update job, or an update job has notbeen requested, the process 1300 proceeds to block 1314.

At block 1314 a purchase request is generated by a user and submitted orautomatically generated. In some embodiments, the purchase request isreviewed and approved, however not all purchase requests may require anapproval. At block 1318 configurable adapters and middleware may be usedto share data between various applications and/or platforms tofacilitate the purchase of the product or service and create appropriaterecords of the purchase for accounting, tax, or other purposes.

At block 1318, approval for the purchase in question is requested andobtained. It should be understood that in some embodiments, requestingand/or obtaining approval may occur before, during, or after data isshared between the various platforms and/or applications creatingrecords for the purchase. At block 1320, the order is submitted andprovided to the vendor (e.g., via the order API). At block 1322 thevendor may confirm the order and provide shipping information, which maybe received by the shipment API. At block 1324 the shipping informationmay be forwarded to the user that requested the order.

Though FIGS. 23-26 and the corresponding discussion above are directedto a framework for managing purchases using the configurable adapters tofacilitate the exchange of data between platforms, it should beunderstood that this is just one possible example of how configurableadapters may be used to build up large, complex frameworks of platformsand/or applications to perform one or more tasks of an enterprise.Accordingly, it should be understood that many other embodiments offrameworks that utilize configurable adapters to facilitate the exchangeof data between platforms are also envisaged.

Configurable adapters may be used in conjunction with middleware toshare data between various platforms and/or applications without a user,developer, or IT agent writing one or more scripts to facilitate thesharing of data. Further, as various platforms and applications areupdated, the configurable adapters and middleware may also dynamicallyupdate so a user does not have to spend time updating a script to workwith the updated platforms/applications. Using configurable adapters andmiddleware, large complex frameworks of many platforms/applications maybe designed to perform various functions of an enterprise ororganization. For example, as discussed with regard to FIGS. 23-26, sucha framework may be designed to pull product information from variousvendors or third parties, as well as promotional offers for thoseproducts. The product and offer data may be combined, processed, andlisted in a product catalog, which users may use to shop for and orderproducts or services. The configurable adapters and middleware may thenbe used to allow platforms and/or applications used by the enterprise toshare data about the order and create appropriate records (e.g., forbook keeping, accounting, taxes, facilities, etc.). Accordingly, the useof configurable adapters and middleware may significantly reduce or eveneliminate the amount of script writing and other software developmentdone to create a complex framework of platforms and/or applications toperform complex tasks within an enterprise.

The specific embodiments described above have been shown by way ofexample, and it should be understood that these embodiments may besusceptible to various modifications and alternative forms. It should befurther understood that the claims are not intended to be limited to theparticular forms disclosed, but rather to cover all modifications,equivalents, and alternatives falling within the spirit and scope ofthis disclosure.

The techniques presented and claimed herein are referenced and appliedto material objects and concrete examples of a practical nature thatdemonstrably improve the present technical field and, as such, are notabstract, intangible or purely theoretical. Further, if any claimsappended to the end of this specification contain one or more elementsdesignated as “means for [perform]ing [a function] . . . ” or “step for[perform]ing [a function] . . . ”, it is intended that such elements areto be interpreted under 35 U.S.C. 112(f). However, for any claimscontaining elements designated in any other manner, it is intended thatsuch elements are not to be interpreted under 35 U.S.C. 112(f).

1. A system, comprising: a non-transitory memory; and one or morehardware processors configured to read instructions from thenon-transitory memory to perform operations comprising: receiving, via aproduct model API, product model data for a product sold by a vendor;receiving from the vendor, via an offer API, offer data corresponding toone or more promotional offers for the product; processing, via a dealhub, the offer data; generating a catalog item for the product; anddisplaying the catalog item within a catalog.
 2. The system of claim 1,wherein the operations comprise: receiving a purchase request for theproduct; generating a purchase order based on the purchase request; andsending, via an order API, the purchase order to the vendor.
 3. Thesystem of claim 2, wherein the operations comprise: generating purchasedata based on the purchase request or the purchase order; storing thepurchase data in a first table of a first platform; and copying, via amiddleware instance, the purchase data to a destination locationspecified by a configurable adapter, wherein the destination locationcomprises a second table of a second platform.
 4. The system of claim 1,wherein the operations comprise: extracting price data for the productfrom the offer data; storing the price data for the product in a pricelog; and analyzing the price data stored in the price log to recognizeone or more trends in the price data.
 5. The system of claim 4, whereinthe operations comprise forecasting a future price of the product basedon the analysis of the price data in the price log.
 6. The system ofclaim 1, wherein the deal hub is configured to consider one or moreratings for the product in processing the offer data.
 7. The system ofclaim 1, wherein the operations comprise receiving the offer data fromone or more social media platforms.
 8. The system of claim 1, whereinthe operations comprise receiving the offer data from one or more couponservices.
 9. A system, comprising: a non-transitory memory; and one ormore hardware processors configured to read instructions from thenon-transitory memory to perform operations comprising: generating agraphical user interface, wherein the graphical user interface isconfigured to display a plurality of catalog items for a plurality ofrespective products, wherein each of the catalog items is created basedon product model data received from a vendor by a product model API andpromotional offer data received from the vendor via an offer API; andreceiving a purchase request for one of the plurality of respectiveproducts.
 10. The system of claim 9, wherein the operations comprise:generating a purchase order based on the purchase request; and sending,via an order API, the purchase order to the vendor.
 11. The system ofclaim 10, wherein the operations comprise: generating purchase databased on the purchase request or the purchase order; storing thepurchase data in a first table of a first platform; and copying, via amiddleware instance, the purchase data to a destination locationspecified by a configurable adapter, wherein the destination locationcomprises a second table of a second platform.
 12. The system of claim9, wherein the operations comprise: extracting price data for a productof the plurality of respective products from the promotional offer data;storing the price data for the product in a price log; and analyzing theprice data stored in the price log to recognize one or more trends inthe price data.
 13. The system of claim 12, wherein the operationscomprise forecasting a future price of the product based on the analysisof the price data in the price log.
 14. The system of claim 9, whereinthe system is configured to consider one or more ratings for the productin processing the promotional offer data.
 15. The system of claim 9,wherein the operations comprise receiving the promotional offer datafrom one or more social media platforms or one or more coupon services.16. A method, comprising: receiving, via a product model API, productmodel data for a product sold by a vendor; receiving from the vendor,via an offer API, offer data corresponding to one or more promotionaloffers for the product; processing, via a deal hub, the offer data;generating a catalog item for the product; and displaying the catalogitem within a catalog.
 17. The method of claim 16, comprising: receivinga purchase request for the product; generating a purchase order based onthe purchase request; and sending, via an order API, the purchase orderto the vendor.
 18. The method of claim 17, comprising: receiving apurchase request for the product; generating a purchase order based onthe purchase request; and sending, via an order API, the purchase orderto the vendor.
 19. The method of claim 16, comprising: extracting pricedata for the product from the offer data; storing the price data for theproduct in a price log; analyzing the price data stored in the price logto recognize one or more trends in the price data; and forecasting afuture price of the product based on the analysis of the price data inthe price log.
 20. The method of claim 16, wherein processing the offerdata considering one or more ratings for the product.